-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open jobs #740
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! ❤️
And even though it was a 1k line commit as usual 😂 This time it was relatively easy to review :)
A few additional comments:
- When I try to submit into a closed job, it crashes with a backtrace:
./hq job submit hostname
./hq job submit --job 1 hostname
Error: Received error: "Job 1 is not open"
<backtrace>
Same when a job is not found and when you attach an array job with a task ID that already exists. It should print some nicer error instead.
- When a new submit is attached to an existing job, we should print a different message than this:
Job submitted successfully, job ID: 2
. It should say something like "New task(s) were attached to job 2".
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Left a few more nits.
I think that all issues have been resolved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this is really cool.
This PR implemented open jobs.
NOT IMPLEMENTED YET: Dependencies between different submits into the same job. The server & scheduler is ready for this, mostly what is missing is to prepare an interface for submitting such tasks).